home *** CD-ROM | disk | FTP | other *** search
/ SGI Performance Co-Pilot 1.3 / SGI Performance Co-Pilot 1.3.iso / dist / dist6.4 / pcp.idb / usr / share / catman / u_man / cat3 / PMAPI / pmgetarchiveend.z / pmgetarchiveend
Text File  |  1997-04-03  |  4KB  |  67 lines
  1.  
  2.  
  3.  
  4. PPPPMMMMGGGGEEEETTTTAAAARRRRCCCCHHHHIIIIVVVVEEEEEEEENNNNDDDD((((3333))))                                          PPPPMMMMGGGGEEEETTTTAAAARRRRCCCCHHHHIIIIVVVVEEEEEEEENNNNDDDD((((3333))))
  5.  
  6.  
  7.  
  8. NNNNAAAAMMMMEEEE
  9.      ppppmmmmGGGGeeeettttAAAArrrrcccchhhhiiiivvvveeeeEEEEnnnndddd - locate logical end of file for an archive log
  10.  
  11. CCCC SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
  12.      ####iiiinnnncccclllluuuuddddeeee <<<<ppppccccpppp////ppppmmmmaaaappppiiii....hhhh>>>>
  13.  
  14.      iiiinnnntttt ppppmmmmGGGGeeeettttAAAArrrrcccchhhhiiiivvvveeeeEEEEnnnndddd((((ssssttttrrrruuuucccctttt ttttiiiimmmmeeeevvvvaaaallll ****ttttvvvvpppp))));;;;
  15.  
  16.      cccccccc ............ ----llllppppccccpppp
  17.  
  18. DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
  19.      Assuming the current PMAPI context is associated with an archive log,
  20.      ppppmmmmGGGGeeeettttAAAArrrrcccchhhhiiiivvvveeeeEEEEnnnndddd will attempt to find the logical end of file (after the
  21.      last complete record in the archive), and return the last recorded
  22.      timestamp via _t_v_p.  This timestamp may be passed to ppppmmmmSSSSeeeettttMMMMooooddddeeee(3) to
  23.      reliably position the context at the last valid log record, e.g. in
  24.      preparation for subsequent reading in reverse chronological order.
  25.  
  26.      For archive logs that are not concurrently being written, the physical
  27.      end of file and the logical end of file are co-incident.  However if an
  28.      archive log is being written by ppppmmmmllllooooggggggggeeeerrrr(1) at the same time an
  29.      application is trying to read the archive, the logical end of file may be
  30.      before the physical end of file due to write buffering that is not
  31.      aligned with the logical record boundaries.
  32.  
  33.      ppppmmmmGGGGeeeettttAAAArrrrcccchhhhiiiivvvveeeeEEEEnnnndddd returns an error less than zero if the context is neither
  34.      valid, nor associated with an archive, or the archive is seriously
  35.      corrupted.  Otherwise, the return value is 0 if there has been no change
  36.      of state since the last call, or 1 if the logical end of file has
  37.      advanced since the last call.
  38.  
  39.      In the absence of an error, the result returned via _t_v_p is well-defined.
  40.  
  41.      ppppmmmmGGGGeeeettttAAAArrrrcccchhhhiiiivvvveeeeEEEEnnnndddd preserves the positioning state of the log file prior to
  42.      this function call.
  43.  
  44. SSSSEEEEEEEE AAAALLLLSSSSOOOO
  45.      PPPPMMMMAAAAPPPPIIII(3), ppppmmmmFFFFeeeettttcccchhhh(3), ppppmmmmFFFFeeeettttcccchhhhAAAArrrrcccchhhhiiiivvvveeee(3), ppppmmmmGGGGeeeettttAAAArrrrcccchhhhiiiivvvveeeeLLLLaaaabbbbeeeellll(3) and
  46.      ppppmmmmSSSSeeeettttMMMMooooddddeeee(3).
  47.  
  48. DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
  49.      PPPPMMMM____EEEERRRRRRRR____NNNNOOOOCCCCOOOONNNNTTTTEEEEXXXXTTTT
  50.           the current PMAPI context is either invalid, or not associated with
  51.           an archive log
  52.  
  53.      PPPPMMMM____EEEERRRRRRRR____LLLLOOOOGGGGRRRREEEECCCC
  54.           the archive is sufficiently damaged, that not a single valid record
  55.           can be found
  56.  
  57.  
  58.  
  59.  
  60.  
  61.  
  62.  
  63.                                                                         PPPPaaaaggggeeee 1111
  64.  
  65.  
  66.  
  67.